home *** CD-ROM | disk | FTP | other *** search
- Path: druid.borland.com!usenet
- From: pete@borland.com (Pete Becker)
- Newsgroups: comp.lang.c++
- Subject: Re: Borland 5.0 16-bit Linker Problems
- Date: 10 Apr 1996 21:58:50 GMT
- Organization: Borland International
- Message-ID: <4khauq$o5e@druid.borland.com>
- References: <4kbnrg$ofr@Grouper.Exis.Net> <316B8C76.381A@craft.camp.clarkson.edu> <316C06E9.1FF4@crc.ricoh.com>
- NNTP-Posting-Host: pbecker.borland.com
- Mime-Version: 1.0
- Content-Type: Text/Plain; charset=ISO-8859-1
- X-Newsreader: WinVN 0.99.5
-
- In article <316C06E9.1FF4@crc.ricoh.com>, jamey@crc.ricoh.com says...
- >
- >Yogerson Falcon wrote:
- >>
- >> > After loading the patch, I found I still could not link 16 bit code.
- >> > After some more reading, The CONAGENT.EXE properties where set to the
- >> > following:
- >> > Program: Close on Exit was set.
- >> > Memory: Total, Intial Environment, DPMI Memory
- >> > Set to Auto
- >> >
- >>
- >> I been having some problem compiling 16-bit application under BC5.0
- >> (Development Suite).. I have 16 MB (As the BC5.0 requires) and Win 95... But
- w
- >hen
- >> compiling a short 16-bit program the linker gave an "out of memory" error ..
- >> However, for some reason when you install only BC5.0 (none of the extras,
- whon
- >ever
- >> is using the Development Suite), then restart the computer and run the
- unistal
- >l
- >> program for BC5.0 (which will die after unregistering BC5.0), the linker
- works
- >;
- >> however, if you install the patch the linker start giving the "out of
- memory"
- >> error (the only way to make work again is to reinstall Win 95, apparently
- the
- >> patch corruptes some Win 95 files, and then reinstall BC5.0).
- >
- >i just installed BC++ 5.0 and the patch (bc50p1) and ran into the same problem
- >described above. i called borland and they asked me to run the program
- CONAGENT
- >.EXE
- >that comes with windows and is located in the \win95\system directory. the
- guy
- >from
- >tech support had me make sure that the conagent PIF file (i.e. shortcut in
- w95)
- >was
- >there as well. the properties for conagent under "program" must be set to
- "clos
- >e on
- >exit" and in the memory section, set to "total = auto" and "initial
- environment
- >=
- >auto". he had me run the program once then reboot my machine. i asked him
- what
- > the
- >conagent was and he had no idea and asked around the shop and nobody could
- tell
- >him.
- > there is a brief explanation of this process in the readme.txt file in \bc5,
- se
- >arch
- >for "out of memory". anyway, i do not have the problem anymore but would
- really
- > like
- >to know why and how this resolved it. also, they suggested that i create all
- ne
- >w
- >project files :-( currently, my "out of the box" experience with this latest
- bo
- >rland
- >release has been a sour one. i have been using borland c++ for years. when i
- g
- >et a
- >new release like this one i expect to be able to a) load my old project files
- an
- >d b)
- >for my code to compile with minimal effort. so far, i cannot get my 16bit
- code
- >to
- >link. i am getting errors like "automatic data segment exceeds 64k" and that
- so
- >me of
- >my library objects have not been found. if anybody's having any success with
- th
- >is
- >release, please let us know what you've done to make it work.
-
- CONAGENT is the Windows 95 utility that handles running 16-bit applications
- from 32-bit applications. Windows 95 comes configured in a way that doesn't
- work with BC++ 5.0.
- "Automatic data segment exceeds 64k" comes up because some things have
- grown, most likely in the runtime library. Chances are that your application
- had close to 64k of data with 4.5, and it's now outgrown your memory model. Try
- it in large or compact.
-
-